-
Notifications
You must be signed in to change notification settings - Fork 234
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Linux case fixes #106
Linux case fixes #106
Conversation
Thank you for your contributions, Alex. After these changes, does XenCenter build and run correctly on Mono? One earlier contributor got it to compile, but it wouldn't run. Also, I'm wondering if it would be better not to change the case of any filenames, just the references to them. What do you think? |
Also, have you verified that a clean check-out still compiles under Visual Studio, or do we need to test that? |
You would need to test Visual Studio (however the changes are pretty minimal and Visual Studio shouldn't really even notice) I don't have any windows machines to test on. I also need to mention that i'm no .NET / C# developer, so take anything I push with a grain of salt :-) This gets 99% of stuff building once defining the package requirements through mono-develop. (requirements in #3) I am running into a "No element named ListViewItemCount could be found" error at the end of the build while it is building resources, still looking into that one. I'm honestly suprised that Citrix didn't port this to Mono / Linux, seems like an easy port that would of increased the usebase. I know we would of deployed XenServer at my previous job if there was a way to manage it from Linux. :-\ |
Actually, it looks like i'm pretty much redoing the work done here: https://github.com/hoerup/xenadmin/commit/dca9a0e80069d10c7a74fcf76cdd016ddc08e47e |
(however my patches are better :-) |
actually, hoerup did more work and converted the C++ splash to C#. Let me redo my fork using his work. |
The thing is, neither hoerup nor ko-85 (later in that thread) actually got it running. So I suspect there's more than just changing the filenames. |
eh. Giving up for now. .NET / C# is a mess outside of Windows. All of this stuff needs cleaned up and refactored. Long-term developing towards Mono may be a good plan as it is a lot more portable vs Microsoft's .NET. Current issue on my fork @ http://github.com/kallisti5/xenadmin
|
That's a shame. Maybe I should start a thread where people can share their experiences of what problems they encountered when porting to Mono, and what solutions they have found. |
One thing is getting the thing to compile - getting it running is a whole other task. |
A series of case issues with the build system. These patches let me build with Mono after going through and adding missing packages (XML-RPC.net, etc)